| ||
Sat 2024-12-21
Fri 2024-12-20
Thu 2024-12-19
Wed 2024-12-18
hydroxychloroquine fraud withdrawn Tue 2024-12-17
Sun 2024-12-15
Sat 2024-12-14
Fri 2024-12-13
Thu 2024-12-12
Tue 2024-12-10
Search
Archives
2023
12 11 10 09 08 07 06 05 04 03 02 01
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
One good site
MDN
Nelson Minar
Blog licensed under a Creative Commons License
|
It struck me that there's one more big risk that MS is taking with
.NET. Will that consumers really pay $25-$50 a year? If it works, then
someone will finally crack the nut of getting people to pay for things
on the Internet. But Microsoft is taking a huge (and uncustomary) risk
in trying to be the first to make it work. As a developer/user, I feel
they're already making mistake in charging
developers for access to My Services. How will ordinary consumers feel?
Obvious counter-strategy: build a totally free alternative service. Plan to give it away the first few years, then either start charging (the Salon model) or monetize the service some other way (the MSIE model). This strategy is high risk, and currently unfashionable. But companies like IBM, Sun, and AOL could afford to do it. The funny thing is I like the idea of MS charging for My Services. It puts the expectations in the right place; my service belongs to me, I pay for it. I hate the way most "free" services take their toll in turning my data into a marketing channel. MS has promised not to do this. If someone follows with a free version, they should give the same protection to consumers. Maybe this is a pipe dream. |
|
